Systems and methods for bot-based automated invoicing and collection

ABSTRACT

In one embodiment, in an information processing apparatus, comprising at least one computer processor, a Bot executed by the at least one computer processor may perform the following: (1) receiving invoice information for an invoice for a payor, the invoice information comprising an invoice amount and a due date; (2) electronically communicating a payment reminder comprising the invoice amount and the due date to the payor in a chat interface; and (3) providing a payment interface in the chat interface.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/554,679, now U.S. Pat. No. 11,544,686, filed Aug. 29, 2019, whichclaims the benefit of U.S. Provisional Patent Application Ser. No.62/731,139, filed Sep. 14, 2018, the disclosure of which is herebyincorporated by reference in its entirety.

BACKGROUND OF THE INVENTION 1. Field of the Invention

Embodiments are directed to systems and methods for bot-based automatedinvoicing and collection.

2. Description of the Related Art

Many businesses may have thousands of invoices due per month. Manuallycollecting and negotiating each invoice is expensive in time, labor andcost. This may result in invoices not being paid, resulting in a loss ofrevenue.

SUMMARY OF THE INVENTION

Systems and methods for bot-based automated invoicing and collection aredisclosed. In one embodiment, in an information processing apparatus,comprising at least one computer processor, a Bot executed by the atleast one computer processor may perform the following: (1) receivinginvoice information for an invoice for a payor, the invoice informationcomprising an invoice amount and a due date; (2) electronicallycommunicating a payment reminder comprising the invoice amount and thedue date to the payor in a chat interface; and (3) providing a paymentinterface in the chat interface.

In one embodiment, the invoice may be overdue or coining due.

In one embodiment, the method may further include automaticallyidentifying a payment incentive; and communicating the payment incentiveto the payor in the chat interface. The payment incentive may be adiscount on the invoice amount, a discount on a future invoice amount,etc. The payment incentive may be identified based on a past interactionwith the payor.

In one embodiment, the method may further include electronicallycommunicating a link to a payment modality to the payor.

In one embodiment, the method may further include automaticallynegotiating with the payor using natural language processing.

In one embodiment, the method may further include updating a payorrecord with a result of the electronic communication.

According to another embodiment, in an information processing apparatus,comprising at least one computer processor, a Bot executed by the atleast one computer processor may perform the following: (1) monitoring areal-time communication between a buyer and a seller; (2) uponactivation to take an order, electronically prompting the buyer or theseller for order details for an order being placed by a buyer, whereinthe order details comprise an identification of a good or service, aquantity, a price, and a payment method; (3) receiving the orderdetails; and (4) communicating the order details to a backend system forfulfillment.

In one embodiment, the communication may be an electronic textcommunication, a voice communication, a voice communication is over anelectronic device, a video conference, an Internet-based meeting, etc.

In one embodiment, the Bot may be automatically activated to receive theorder details based on a context of the communication, may be manuallyactivated to receive the order details, etc.

In one embodiment, the method may further include automaticallyidentifying an upsell; and presenting the upsell to the buyer. Theupsell may be based on a buyer interest, a successful upsell with aprior buyer of the good or service, etc.

In one embodiment, the Bot may be executed by a portable electronicdevice.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to facilitate a fuller understanding of the present invention,reference is now made to the attached drawings. The drawings should notbe construed as limiting the present invention but are intended only toillustrate different aspects and embodiments.

FIG. 1 depicts a system for bot-based automated invoicing and collectionaccording to one embodiment;

FIG. 2 depicts a method for bot-based automated invoicing and collectionaccording to one embodiment;

FIGS. 3A-3C depict exemplary screenshots according to embodiments; and

FIG. 4 depicts a method of bot-based interaction according to oneembodiment.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments are generally directed to systems and methods for bot basedautomated invoicing and collection.

In embodiments, a computer program (e.g., a Bot) may be used tonegotiate and collect invoices from one or more (e.g., thousands) ofvendors at substantially simultaneously. The Bot may identify an invoicethat is coining due, send a reminder to the payor, present a paymentmechanism to facilitate the payment, provide alternate paymentmechanisms (e.g., pay some now, pay some later, etc.), provide paymentincentives (e.g., provide a discount for prompt payment), etc.

In one embodiment, the Bot may collect and aggregate analytics onpayors, such as average time for payment, etc. Embodiments mayincorporate the analytics into an organization's cash flow managementsystem, and may provide information on when a payment is likely to bereceived based on the payor's payment history.

In embodiments, machine learning and/or artificial intelligence may beused to provide analysis on the analytics.

Embodiments may automate invoicing by receiving an image of a paperinvoice and populating data fields in a collection system withinformation from the invoice.

Embodiments may further prioritize invoices when there are multipleinvoices due. For example, the Bot may prioritize invoices based on duedate, amount, or any other criteria as is necessary and/or desired.

Referring to FIG. 1 , a system for Bot-based automated invoicing andcollection is disclosed according to one embodiment. System 100 mayinclude payor 110, payee 120, and financial service provider 130. Payor110 may receive a good or service from payee 120. Payor 110 and payee120 may be any suitable entities, including individuals, groups ofindividuals, companies, organizations, etc. For example, payor 110 maybe a buyer, and payee 120 may be a seller.

Payor 110 and payee 120 may each be associated with electronic devices115, 125, respectively. Electronic devices 115 and 125 may be anysuitable electronic devices, including computers (e.g., desktop,notebook, tablet, etc.), smartphones, smart watches, Internet of Things(IoT) appliances, etc.

Financial service provider 130 may be a financial institution or FinTechused by payee 120 that provides invoicing, terms, negotiations, billing,payment, order financing, order factoring, collection services, etc.Financial service provider 130 may host server 132 that executescollections program 134. Server 132 may be based with the financialinstitution 130, or it may be a cloud-based server.

Collections program 134 may be a computer-based program that may manageinvoices for payee 110. In one embodiment, payor 110 and payee 120 maycommunicate with collections program 134 using mobile devices 115 and125, respectively.

Collections program 134 may execute bot 136 that may communicate withpayor 110 in order to resolve an outstanding invoice. In one embodiment,bot 134 may further communicate with payee 120 to, for example, requestinvoice information, provide updates, etc.

Referring to FIG. 2 , a method for bot-based automated invoicing andcollection is disclosed according to one embodiment.

In step 205, a payee may enter an invoice into a collection programexecuted by one or more servers, computers, Internet of Things (IoT)appliances, etc. In one embodiment, the invoice may be manually entered,may be provided by an invoicing system, may be received as an image(e.g., a photograph), etc. In another embodiment, a Bot executed by thecollections program may receive a purchase order for a purchase.

In embodiments, the invoice data may be received through, for example,voice order, chat order, text message, email message, social mediaprofile, social media message or from a buy modal or button, in which,for example, the Bot may take the order, fulfill it and send an invoicefor payment. At least some of the invoice data may be received from apayment method such as Apple Pay, Samsung Pay, credit card, debit card,banking account info, checking/ACH info, a photo or scan of a check toOCR the billing, account, and routing number, etc.

In embodiments, combinations of one or more of these methods/mechanisms,and may “piece” together the order information, who the order is from,identity, address, contact info, billing info, shipping info, andpayment means. Based upon this information, the Bot may create anelectronic invoice with terms of delivery and payment as well as apayment method, date and invoice identification/tracking/referencenumber, etc.

In step 210, if not already in a collections system, the Bot may enterthe invoice into a collection system. This may permit the collectionssystem or engine to update or change an invoice based upon, for example,Bot negotiations with the payor. For example, if a payor decides tocancel all or a portion of the order, or return goods, then the invoicemay be updated.

In step 215, the Bot may send a payment request or reminder with one ormore payment options and incentives to the payor. In one embodiment, theBot may send this to the payor with the initial invoice, as a paymentdue date approaches, etc.

In one embodiment, the Bot may consider the payor's payment terms intiming the reminder. For example, if the payor is on a 60-day paymentterm, the Bot may base the reminder on that payment term.

In one embodiment, the Bot may provide payment options to the payor,such as payment amounts, payment modalities, etc. For example, the Botmay provide links to ACH payments, credit card payments, and otherpayment modalities to the payor.

In one embodiment, the Bot may provide payment options in order to splitthe invoice into more than one payment. For example, if the payor splitsthe invoice into multiple payments, the Bot may apply a fee.

In one embodiment, the Bot may provide an incentive for timely or earlypayment, such as a discount on the current invoice, a discount on afuture invoice, etc.

In one embodiment, the Bot may send addition reminders as the paymentdue date approaches, automatically apply late fees, etc. as is necessaryand/or desired.

In one embodiment, the Bot may provide the payee with paymentnotification, such as paid payments, overdue payments, etc. An exampleof such a notice indicting that there are overdue payments is providedin FIG. 3A.

In one embodiment, the Bot may prioritize outstanding invoices for thepayee, and may recommend one or more action to take with the payor. Forexample, referring to FIG. 3B, the Bot may identify the invoice, thepoint of contact, the amount due, the status, etc. and may provideoptions, such as negotiate, re-send invoice, call, etc.

Referring again to FIG. 2 , in step 220, the Bot may interact with apayor. In one embodiment, the Bot may interact in a message or chat-typeinterface in which it may use artificial intelligence, natural languageprocessing, etc. to interact with the payor. An example of such aninterface and interaction is provided in FIG. 3C.

In one embodiment, the tone and/or aggressiveness of the Bot's chat maybe based on the amount of the invoice, how long the invoice is overdue,prior success/failure of collection efforts (including using the Bot),etc.

In one embodiment, machine learning may be used to predict the amount ofan incentive that is likely to result in the payor paying the invoice.The Bot may then set the negotiation strategy to get to this point, suchas by starting with a lower incentive than the predicted incentive.

In step 225, the Bot may update information for the payor based on theinteraction. For example, if the Bot was successful, the Bot may updatethe payor's account to reference a successful interaction, may apply anydiscounts or reductions to the invoice, etc. It may further store arecord of the interaction.

The Bot may further inform the payee of the outcome of the interaction.

If the Bot was unsuccessful, the Bot may update the payor's account toreference the results of the interaction, including a record of thecommunication, what was offered, the response, etc.

The Bot may further inform the payee of the outcome of the interaction.

In one embodiment, the Bot may escalate the invoice as necessary (e.g.,provide to a collections agency, etc.).

Referring again to FIG. 2 , in step 225, the collection system and/orthe Bot (or a combination of Bots) may aggregate data for one or morepayor, such as the timing of payment, the amount of payment, number ofreminders, and any other data as is necessary and/or desired. The datamay be used to predict each payor's payment timing, such as the timingof an expected payment. In one embodiment, the data may be used tograde, rank, and/or recommend payors. For example, a payor that alwayspays on time may be given an “A” or similar grade, and may be rankedhighly in field. Conversely, a payor that does not pay on time may begiven a lower ranking.

In embodiments, rankings and insights on payment performance may be usedas leverage and incentive by the Bots during collections. Rankings mayprevent other businesses from doing business with the poorly-rankedpayor. Conversely, a highly ranked payor with a record of paying in fullon time may use this info, insights and ranking to negotiate betterterms with payees.

In embodiments, a user dashboard or other interface may be used to setand adjust preferences or settings for collecting and negotiatinginvoices and payments. For example, the settings may be set toaggressive in frequency and in tone, may be set to friendly in frequencyand tone, etc. In embodiments, the settings may be set or adjusted basedon analytics, insights and grading, creditworthiness intelligencecollected by the system through previous collections and negotiations orthough external credit rating, business rating and social ratingsystems, as well as any other information as is necessary and/ordesired.

In addition, other payee data, such as expected payment dates, may beprovided. Artificial intelligence and/or machine learning may be used toprovide recommendations on payors.

The grades, ranks, and/or recommendations may be presented to payees inorder for them to select a payor.

Referring to FIG. 4 , a method for Bot-assisted transactions is providedaccording to one embodiment. In step 405, a user, such as a seller, mayengage in an electronic communication with another party, such as abuyer. In one embodiment, the roles of the entities may not beestablished at the time that the communication was initiated; the rolesmay be determined based on the communication.

In one embodiment, the communication may be a voice-based communication,a text based communication (e.g., SMS/text, chat, instant message,email, etc.), a video conversation, a video conference, anInternet-based meeting, etc. In another embodiment, the communicationmay be a face-to-face communication.

In step 410, one of the parties (e.g., the buyer) expresses an intentionto place an order. In one embodiment, the buyer may use certain termsindicating the desire to place an order, such as “I would like to buy”or “I am ordering.” In one embodiment, the seller may also use certainterms indicating that an order is taking place.

In one embodiment, the Bot may be “listening” to electroniccommunications using an electronic device (e.g., voice, text, etc.). Inanother embodiment, the Bot may listen to person-to-personcommunications. For example, the Bot may be executed in a mobileelectronic device, in an Internet of Things (IoT) appliance, at a pointof sale device, in a computer, etc.

In step 415, the Bot may be activated to take the order. In oneembodiment, the Bot may be automatically activated based on recognizingthat an order is being placed. Natural language processing may be usedto assist the Bot in identifying the intent to place the order.

In another embodiment, the Bot may be activated by the seller. Forexample, the Bot may be activated by the seller issuing a verbal or textinstruction to the Bot, by manually activating the Bot on an electronicdevice, etc.

In step 420, the Bot may take order details from the buyer. In oneembodiment, the seller may participate in the order-taking; in anotherembodiment, the seller may effectively hand the communication off to theBot for taking the order.

In one embodiment, the Bot may take all necessary information tocomplete the transaction, including quantity, buyer information, paymentinformation, etc. In one embodiment, the Bot may upsell additional goodsor services.

In step 425, the Bot may complete the sale, and may communicate the saleto fulfillment, a backend system, etc. as necessary. In one embodiment,the Bot may return the call to the seller to continue the conversation.

In one embodiment, although buyer and seller are used to describe theparticipants, it should be recognized that the buyer may use a Bot toplace an order, and the Bot may provide the seller with the necessaryinformation (e.g., buyer information, payment information, etc.).Further, the Bot may assist in person-to-person transactions, where afirst person wants to send money to a second person. The Bot may be usedto identify accounts for either party and providing the transaction toone of the person's financial institution, to a FinTech, etc. so thatthe transaction may be completed.

In one embodiment, a Bot can also be in “Always selling” mode, where itlistens to all conversations and electronic communications for salesopportunities. The Bot can record and share notes based upon meetings,conversations and identify opportunities for follow up, and mayrecommend sales opportunities and may initiate orders based uponmeetings, conversations and electronic conversations.

In embodiments, a Bot may be provided to upsell goods or services,engage with customers, negotiate, close sales, and provide analytics onsales, performance, and conversion rates. In one embodiment, the upsellmay be based on a prior buyer purchase.

A Bot may enable sales engagement and closing at scale. A “Closer Bot”may personally engage, sell and close thousands or millions of potentialcustomers at once. An example scenario involving the use of a Closer Botis provided in FIG. 5 .

Another example scenario involving a Closer Bot is as follows. An eventspromoter may prepare for a sales campaign by inputting content anddetails of the campaign, such as name of product or service,description, pictures, video, links, price, time frame, URL links andadditional products and services into the Closer Bot dashboard. Thepromoter may import contacts from the promoter's phone, and may initiatethe Closer Bot. Using the Closer Bot, the promoter may set or adjustincentive parameters, such as hot event, celebrity, limited entry, VIPupgrade, overflow party if sold out, after party, and may send theinvites.

The customer may receive an invite via text/iOS messenger/Facebookmessenger, voice interface, or any form of messaging or communicationand may view the content. Interaction by the user, such as expanding thedetails to reveal info, pricing, etc. may initiate the Closer Bot. Anexample dialog is provided below:

-   -   Closer Bot: This is a hot event and selling fast, we have these        celebrities attending.    -   Customer: Oh wow nice! I want to go.    -   Closer Bot: How many tickets do you need? You should bring your        whole squad.    -   Customer: Right, good idea, I'll take 5.    -   Closer Bot: Perfect!    -   The Closer both then sends a message with a credit card        processing modal that captures credit card info through texting        numbers/picture of card/Apple Pay/Chase Pay/tap link to process        online, or sends tickets with invoice to pay.    -   Bot: Done! Here are your 5 tickets! (Bot sends image of tickets        or link to download or print tickets).    -   Bot: For your squad, I would recommend VIP access, you get to        sit right next to the celebrities.    -   Customer: Of course I want VIP! I'll pay. (Bot responds by        sending another payment modal).    -   Bot: Perfect, done again, here's your VIP access. (Bot sends        image of upgraded tickets, or password, or code, or link to        download or print tickets). Go through the restaurant,        downstairs past the bathrooms and through the kitchen you'll see        Frantz, show him your VIP access and you're in.    -   Customer: OMG you're awesome!    -   Bot: Nah, you're awesome, thank you and enjoy!    -   Bot: Let me know if you have friends that want to go as well and        I'll reach out.    -   The Bot proceeds to initiate sales with 5 of customer's friends        and closes 3 and receives 12 more friends to sell, and keeps        going.

Hereinafter, general aspects of implementation of the systems andmethods of the invention will be described.

The system of the invention or portions of the system of the inventionmay be in the form of a “processing machine,” such as a general-purposecomputer, for example. As used herein, the term “processing machine” isto be understood to include at least one processor that uses at leastone memory. The at least one memory stores a set of instructions. Theinstructions may be either permanently or temporarily stored in thememory or memories of the processing machine. The processor executes theinstructions that are stored in the memory or memories in order toprocess data. The set of instructions may include various instructionsthat perform a particular task or tasks, such as those tasks describedabove. Such a set of instructions for performing a particular task maybe characterized as a program, software program, or simply software.

In one embodiment, the processing machine may be a specializedprocessor.

As noted above, the processing machine executes the instructions thatare stored in the memory or memories to process data. This processing ofdata may be in response to commands by a user or users of the processingmachine, in response to previous processing, in response to a request byanother processing machine and/or any other input, for example.

As noted above, the processing machine used to implement the inventionmay be a general-purpose computer. However, the processing machinedescribed above may also utilize any of a wide variety of othertechnologies including a special purpose computer, a computer systemincluding, for example, a microcomputer, mini-computer or mainframe, aprogrammed microprocessor, a micro-controller, a peripheral integratedcircuit element, a CSIC (Customer Specific Integrated Circuit) or ASIC(Application Specific Integrated Circuit) or other integrated circuit, alogic circuit, a digital signal processor, a programmable logic devicesuch as a FPGA, PLD, PLA or PAL, or any other device or arrangement ofdevices that is capable of implementing the steps of the processes ofthe invention.

The processing machine used to implement the invention may utilize asuitable operating system. Thus, embodiments of the invention mayinclude a processing machine running the iOS operating system, the OS Xoperating system, the Android operating system, the Microsoft Windows™operating systems, the Unix operating system, the Linux operatingsystem, the Xenix operating system, the IBM AIX™ operating system, theHewlett-Packard UX™ operating system, the Novell Netware™ operatingsystem, the Sun Microsystems Solaris™ operating system, the OS/2™operating system, the BeOS™ operating system, the Macintosh operatingsystem, the Apache operating system, an OpenStep™ operating system oranother operating system or platform.

It is appreciated that in order to practice the method of the inventionas described above, it is not necessary that the processors and/or thememories of the processing machine be physically located in the samegeographical place. That is, each of the processors and the memoriesused by the processing machine may be located in geographically distinctlocations and connected so as to communicate in any suitable manner.Additionally, it is appreciated that each of the processor and/or thememory may be composed of different physical pieces of equipment.Accordingly, it is not necessary that the processor be one single pieceof equipment in one location and that the memory be another single pieceof equipment in another location. That is, it is contemplated that theprocessor may be two pieces of equipment in two different physicallocations. The two distinct pieces of equipment may be connected in anysuitable manner. Additionally, the memory may include two or moreportions of memory in two or more physical locations.

To explain further, processing, as described above, is performed byvarious components and various memories. However, it is appreciated thatthe processing performed by two distinct components as described abovemay, in accordance with a further embodiment of the invention, beperformed by a single component. Further, the processing performed byone distinct component as described above may be performed by twodistinct components. In a similar manner, the memory storage performedby two distinct memory portions as described above may, in accordancewith a further embodiment of the invention, be performed by a singlememory portion. Further, the memory storage performed by one distinctmemory portion as described above may be performed by two memoryportions.

Further, various technologies may be used to provide communicationbetween the various processors and/or memories, as well as to allow theprocessors and/or the memories of the invention to communicate with anyother entity; i.e., so as to obtain further instructions or to accessand use remote memory stores, for example. Such technologies used toprovide such communication might include a network, the Internet,Intranet, Extranet, LAN, an Ethernet, wireless communication via celltower or satellite, or any client server system that providescommunication, for example. Such communications technologies may use anysuitable protocol such as TCP/IP, UDP, or OSI, for example.

As described above, a set of instructions may be used in the processingof the invention. The set of instructions may be in the form of aprogram or software. The software may be in the form of system softwareor application software, for example. The software might also be in theform of a collection of separate programs, a program module within alarger program, or a portion of a program module, for example. Thesoftware used might also include modular programming in the form ofobject oriented programming The software tells the processing machinewhat to do with the data being processed.

Further, it is appreciated that the instructions or set of instructionsused in the implementation and operation of the invention may be in asuitable form such that the processing machine may read theinstructions. For example, the instructions that form a program may bein the form of a suitable programming language, which is converted tomachine language or object code to allow the processor or processors toread the instructions. That is, written lines of programming code orsource code, in a particular programming language, are converted tomachine language using a compiler, assembler or interpreter. The machinelanguage is binary coded machine instructions that are specific to aparticular type of processing machine, i.e., to a particular type ofcomputer, for example. The computer understands the machine language.

Any suitable programming language may be used in accordance with thevarious embodiments of the invention. Illustratively, the programminglanguage used may include assembly language, Ada, APL, Basic, C, C++,COBOL, dBase, Forth, Fortran, Java, Modula-2, Pascal, Prolog, REXX,Visual Basic, and/or JavaScript, for example. Further, it is notnecessary that a single type of instruction or single programminglanguage be utilized in conjunction with the operation of the system andmethod of the invention. Rather, any number of different programminglanguages may be utilized as is necessary and/or desirable.

Also, the instructions and/or data used in the practice of the inventionmay utilize any compression or encryption technique or algorithm, as maybe desired. An encryption module might be used to encrypt data. Further,files or other data may be decrypted using a suitable decryption module,for example.

As described above, the invention may illustratively be embodied in theform of a processing machine, including a computer or computer system,for example, that includes at least one memory. It is to be appreciatedthat the set of instructions, i.e., the software for example, thatenables the computer operating system to perform the operationsdescribed above may be contained on any of a wide variety of media ormedium, as desired. Further, the data that is processed by the set ofinstructions might also be contained on any of a wide variety of mediaor medium. That is, the particular medium, i.e., the memory in theprocessing machine, utilized to hold the set of instructions and/or thedata used in the invention may take on any of a variety of physicalforms or transmissions, for example. Illustratively, the medium may bein the form of paper, paper transparencies, a compact disk, a DVD, anintegrated circuit, a hard disk, a floppy disk, an optical disk, amagnetic tape, a RAM, a ROM, a PROM, an EPROM, a wire, a cable, a fiber,a communications channel, a satellite transmission, a memory card, a SIMcard, or other remote transmission, as well as any other medium orsource of data that may be read by the processors of the invention.

Further, the memory or memories used in the processing machine thatimplements the invention may be in any of a wide variety of forms toallow the memory to hold instructions, data, or other information, as isdesired. Thus, the memory might be in the form of a database to holddata. The database might use any desired arrangement of files such as aflat file arrangement or a relational database arrangement, for example.

Application Programming Interfaces (APIs) and other softwareintermediaries that allow two applications to communicate may be used.

In the system and method of the invention, a variety of “userinterfaces” may be utilized to allow a user to interface with theprocessing machine or machines that are used to implement the invention.As used herein, a user interface includes any hardware, software, orcombination of hardware and software used by the processing machine thatallows a user to interact with the processing machine. A user interfacemay be in the form of a dialogue screen for example. A user interfacemay also include any of a mouse, touch screen, keyboard, keypad, voicereader, voice recognizer, dialogue screen, menu box, list, checkbox,toggle switch, a pushbutton or any other device that allows a user toreceive information regarding the operation of the processing machine asit processes a set of instructions and/or provides the processingmachine with information. Accordingly, the user interface is any devicethat provides communication between a user and a processing machine. Theinformation provided by the user to the processing machine through theuser interface may be in the form of a command, a selection of data, orsome other input, for example.

As discussed above, a user interface is utilized by the processingmachine that performs a set of instructions such that the processingmachine processes data for a user. The user interface is typically usedby the processing machine for interacting with a user either to conveyinformation or receive information from the user. However, it should beappreciated that in accordance with some embodiments of the system andmethod of the invention, it is not necessary that a human user actuallyinteract with a user interface used by the processing machine of theinvention. Rather, it is also contemplated that the user interface ofthe invention might interact, i.e., convey and receive information, withanother processing machine, rather than a human user. Accordingly, theother processing machine might be characterized as a user. Further, itis contemplated that a user interface utilized in the system and methodof the invention may interact partially with another processing machineor processing machines, while also interacting partially with a humanuser.

It will be readily understood by those persons skilled in the art thatthe present invention is susceptible to broad utility and application.Many embodiments and adaptations of the present invention other thanthose herein described, as well as many variations, modifications andequivalent arrangements, will be apparent from or reasonably suggestedby the present invention and foregoing description thereof, withoutdeparting from the substance or scope of the invention.

Accordingly, while the present invention has been described here indetail in relation to its exemplary embodiments, it is to be understoodthat this disclosure is only illustrative and exemplary of the presentinvention and is made to provide an enabling disclosure of theinvention. Accordingly, the foregoing disclosure is not intended to beconstrued or to limit the present invention or otherwise to exclude anyother such embodiments, adaptations, variations, modifications orequivalent arrangements.

1-19. (canceled)
 20. An electronic device, comprising: a computerprocessor; and a memory storing a collection bot computer program;wherein, when read and executed by the computer processor, thecollection bot computer program causes the computer processor to:receive invoice information for an invoice for a payor, the invoiceinformation comprising an invoice amount and a due date; display, in achat interface, a payment reminder comprising the invoice amount and thedue date to the payor, wherein the chat interface provides real-timetwo-way messaging with the payor; and provide, a payment interface inthe chat interface.
 21. The electronic device of claim 20, wherein, whenread and executed by the computer processor, the collection bot computerprogram causes the computer processor to: automatically identify apayment incentive; and communicate the payment incentive to the payor inthe chat interface.
 22. The electronic device of claim 21, wherein thepayment incentive is a discount on the invoice amount or a discount on afuture invoice amount.
 23. The electronic device of claim 21, whereinthe payment incentive is identified based on a past interaction with thepayor.
 24. The electronic device of claim 20, wherein, when read andexecuted by the computer processor, the collection bot computer programcauses the computer processor to: electronically communicate a link to apayment modality to the payor.
 25. The electronic device of claim 20,wherein, when read and executed by the computer processor, thecollection bot computer program causes the computer processor to:automatically negotiate with the payor using natural languageprocessing.
 26. The electronic device of claim 20, wherein, when readand executed by the computer processor, the collection bot computerprogram causes the computer processor to: update a payor record with aresult of the payment reminder.
 27. An electronic device, comprising: acomputer processor; and a memory storing a collection bot computerprogram; wherein, when read and executed by the computer processor, thecollection bot computer program causes the computer processor to:monitor a real-time messaging interaction between a buyer and a seller;in response to sensing an order in the real-time messaging interaction,prompt, in a two-way chat interface, the buyer or the seller for orderdetails for an order being placed by a buyer, wherein the order detailscomprise an identification of a good or service, a quantity, a price,and a payment method; receive the order details in the two-way chatinterface; and communicate the order details to a backend system forfulfillment.
 28. The electronic device of claim 27, wherein thereal-time messaging interaction is an electronic text-basedcommunication.
 29. The electronic device of claim 27, wherein thereal-time messaging interaction is a voice communication over anelectronic device.
 30. The electronic device of claim 27, wherein, whenread and executed by the computer processor, the collection bot computerprogram causes the computer processor to: automatically identify anupsell to present to the buyer; and present the upsell to the buyer inthe two-way chat interface.
 31. The electronic device of claim 30,wherein the upsell is based on a buyer interest.
 32. The electronicdevice of claim 30, wherein the upsell is based on a successful upsellwith a prior buyer of the good or service.
 33. A method for Bot-basedselling, comprising: monitoring, by a Bot executed by at least onecomputer processor, a real-time messaging interaction between a firstbuyer and a seller, wherein the Bot comprises a computer program that isprogrammed to monitor the real-time messaging interaction; in responseto sensing an order for an item from the first buyer in the real-timemessaging interaction, electronically prompting, by the Bot in firsttwo-way chat interface, the first buyer for contact information for asecond buyer; receiving, by the Bot, the contact information for thesecond buyer in the first two-way chat interface; contacting, by theBot, the second buyer in a second two-way chat interface; andpresenting, by the Bot, an offer for the item to the second buyer in thesecond two-way chat interface.
 34. The method of claim 33, furthercomprising: sending, by the Bot, a first payment interface for the itemto the first buyer in response to sensing the order from the firstbuyer.
 35. The method of claim 34, wherein the first payment interfaceis sent in the first two-way chat interface.
 36. The method of claim 33,further comprising: sending, by the Bot, a second payment interface forthe item to the second.
 37. The method of claim 36, wherein the secondpayment interface is sent in the second two-way chat interface.
 38. Themethod of claim 33, wherein the item comprises a ticket to an event. 39.The method of claim 33, wherein the contact information for the secondbuyer is imported from a contacts application on an electronic deviceexecuting the first two-way chat interface.